Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[v10] refactor: use ImplicitDiscreteSystem to implement affects in callback systems #3452

Open
wants to merge 57 commits into
base: master
Choose a base branch
from

Conversation

vyudu
Copy link
Member

@vyudu vyudu commented Mar 12, 2025

Close #2639 #2612

@vyudu vyudu marked this pull request as draft March 12, 2025 08:01
@vyudu vyudu force-pushed the callback branch 2 times, most recently from 4a6f2f6 to b7997b0 Compare March 20, 2025 21:28
@vyudu vyudu marked this pull request as ready for review April 2, 2025 14:12
@vyudu vyudu changed the title WIP: refactor: use ImplicitDiscreteSystem to implement affects in callback systems refactor: use ImplicitDiscreteSystem to implement affects in callback systems Apr 2, 2025
@vyudu
Copy link
Member Author

vyudu commented Apr 2, 2025

@ChrisRackauckas @AayushSabharwal This is very close, just needs a release for ImplicitDiscreteSolve and getting all the doc blocks working. One of the FMI tests is failing because the reinitialization isn't accurate enough (like 1.008e-8 but the tolerance is 1e-8), but I am unsure if that is related.

@vyudu vyudu changed the title refactor: use ImplicitDiscreteSystem to implement affects in callback systems [v10] refactor: use ImplicitDiscreteSystem to implement affects in callback systems Apr 3, 2025
@@ -25,6 +25,67 @@ the event occurs). These can both be specified symbolically, but a more [general
functional affect](@ref func_affects) representation is also allowed, as described
below.

## Symbolic Callback Semantics (changed in V10)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
## Symbolic Callback Semantics (changed in V10)
## Symbolic Callback Semantics

Mention that in the NEWS.md file.

@@ -54,6 +54,7 @@ import Moshi
using Moshi.Data: @data
using NonlinearSolve
import SCCNonlinearSolve
using ImplicitDiscreteSolve
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why is this needed as a hard dep?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IDSolve is called in the implicit affect codegen

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

SymbolicDiscreteCallback and SymbolicContiniuousCallback have different affect field names
3 participants